-
Notifications
You must be signed in to change notification settings - Fork 191
DOC-5064 improvements to Jedis production usage advice #1400
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
base: main
Are you sure you want to change the base?
Conversation
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Just a couple of items to validate. I like the checklist short code! Approving now so you're not held up.
Co-authored-by: David Dougherty <[email protected]>
Well spotted, @dwdougherty - thanks! |
JedisClientConfig clientConfig = DefaultJedisClientConfig.builder() | ||
.connectionTimeoutMillis(2000) | ||
.socketTimeoutMillis(2000) | ||
.tcpKeepAlive(true) |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
tcpKeepAlive
is by default through when using DefaultJedisSocketFactory
and is not externally configurable.
DefaultJedisClientConfig
does not expose tcpKeepAlive(true)
method
DOC-5064
I've added four new short sections, partly based on suggestions in Ricardo Ferreira's recent blog post and an experimental "live" checklist. I've also expanded the description of timeouts a bit. All feedback is welcome, as usual, especially regarding the following points: